Skip to content

Conversation

@nextcloud-bot
Copy link
Member

Nextcloud 33

Pending PRs:


  • ⚠: conflicts detected
  • ✅: approved
  • 🔁: changes requested

@nextcloud-bot nextcloud-bot requested a review from a team as a code owner January 22, 2026 09:50
@nextcloud-bot nextcloud-bot added this to the Nextcloud 33 milestone Jan 22, 2026
@nextcloud-bot nextcloud-bot requested review from CarlSchwan, come-nc, leftybournes and provokateurin and removed request for a team January 22, 2026 09:50
@nextcloud-bot nextcloud-bot added the 3. to review Waiting for reviews label Jan 22, 2026
Signed-off-by: Worker Builder <[email protected]>
@Altahrim Altahrim changed the title 33.0.0 rc1 33.0.0 RC1 Jan 22, 2026
@Altahrim Altahrim merged commit cea2613 into stable33 Jan 22, 2026
16 of 19 checks passed
@Altahrim Altahrim deleted the release/33.0.0_rc1 branch January 22, 2026 09:56
@github-actions github-actions bot changed the title 33.0.0 RC1 [stable33] 33.0.0 RC1 Jan 22, 2026
@cherti
Copy link

cherti commented Jan 23, 2026

I am again kindly asking to not be included in another set of PRs that have no relevance for me. I have asked for this in #57545 (comment) already and given that it seems unclear to me how many more rounds of this you are planning to do I would kindly ask again to please arrange that I am not constantly included with something that is not relevant for or related to me at all. Thank you.

@AndyScherzinger
Copy link
Member

As stated last time referring to your comment see #57545 (comment) @cherti, removing the milestone assignment would have done the job. Since you didn't do so back then I took the liberty to do it for you. So from now on you won't be @ mentioned in the such PRs any longer.

@cherti
Copy link

cherti commented Jan 23, 2026

Thank you very much. It doesn't look to me like I can assign anything to any milestone, it is something that would have had to be done from your side anyways, from how it looked from my side. Hence I was irritated why it wasn't done before.

@iasdeoupxe
Copy link

I agree that it is very annoying to get included in such thing completely irrelevant for me automatically / without any involvement from my side.

I even have no idea what "milestone" is and why i should do anything which i'm not involved at all.

@AndyScherzinger
Copy link
Member

@iasdeoupxe removed the milestone form you PR as well, so no more @ mention pings from now on. For both of you (well, any contributor / PR owner) I thought the milestone is visible in the right sidebar of the PR and can be set/unset. Thanks for clarifying that to me 👍

As for your PR I did assign a milestone since I was optimistic I could wrap it up for the release but also lack further detail knowledge on the missing parts.

@iasdeoupxe
Copy link

@AndyScherzinger Thanks for handling 👍

There is something called "Milestone" on my PR at the right side but i have no means to change / update it (and i wouldn't touch it anyway as i have no insights on the purpose of it :-))

@nickvergessen
Copy link
Member

We will discuss to adjust in the future so external contributors are not pinged.
The main intention is to remind people about their started work that will miss the deadline for the upcoming release.
I guess once would be fine, but I agree that every week for all betas/RCs is not helpful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants